I have a server running Server 2008 R2 64bit SP1, its only running some applications and sharing some drives/folder that's it. Yesterday, 12 July 2012 it automatic installed some Windows updates (see image for specific updates: http://i.imgur.com/2y1b6.png), unfortunately after that it won't fully boot anymore. Every time it comes to "Preparing to configure Windows. Do not turn off the computer." it reboots, this keep going in a endless loop. (see image: http://i.imgur.com/FPOEg.png) I started googling and fond this: http://www.sevenforums.com/tutorials/139576-startup-repair-infinite-loop-recovery.html (step 6 to 16) It worked, and I'm now able to boot (for now...) But if I try to start any application or a mmc (e.g. Event Viewer) it just fails (see image for error message: http://i.imgur.com/VBcwS.png). If I reboot the server it just jump right back in to the "Preparing to configure Windows" loop. Thanks In Advance!

Try last known good configuration and see if that makes any difference.I do not represent the organisation I work for, all the opinions expressed here are my own. This posting is provided "AS IS" with no warranties or guarantees and confers no rights.

Beside to Santhosh post, Try to login into the server in safe mode with networking and check for the difference.Regards, Ravikumar P

Thanks for the replays, unfortunately it didn't make any different i still end up ind the loop of death (Preparing to configure Windows)

Hi, Please perform the following steps: Boot your computer from Windows Server 2008 R2 installation DVD. Select your language settings, and then click Next . In the Setup window, click Repair your computer . In the System Recovery Options window, select the operating system, and then click Next . In the System Recovery Options window, click Command Prompt . Type the following commands and press ENTER after each command: icacls c:\windows\winsxs\pending.xml /grant administrators:F del c:\windows\winsxs\pending.xml reg load HKLM\BaseSystem c:\windows\system32\config\system reg delete HKLM\BaseSystem\CurrentControlSet\Control\Session Manager /v SetupExecute reg add HKLM\BaseSystem\CurrentControlSet\Control\Session Manager /v SetupExecute /t REG_MULTI_SZ 7. Type Exit and then press ENTER. 8. In the System Recovery Options window, click Restart . Can you boot into your system now? If the issue persists, please perform a Startup Repair and use bootrec.exe to check the result. For the detailed steps, please refer to the following Microsoft KB article: How to use the Bootrec.exe tool in the Windows Recovery Environment to troubleshoot and repair startup issues in Windows http://support.microsoft.com/kb/927392 Regards,Arthur Li TechNet Community Support

Unfortunately this didn't solve the problem, I now get this blue screen during boot. http://i.imgur.com/I27Xt.png Thank you in advance!

Hi, You may analyze them with Debugging Tools by yourself. You can install it and its Symbol Packages from the following link: http://www.microsoft.com/whdc/Devtools/Debugging/default.mspx WinDbg will tell you the possible cause. For more information, please read Microsoft KB Article: How to read the small memory dump files that Windows creates for debugging http://support.microsoft.com/kb/315263 Collect Minidump Files ================= 1. Click "Start", input "SYSDM.CPL" (without quotation marks) in the Search bar and press Enter. 2. Switch to the "Advanced" tab and click the "Settings" button under "Startup and Recovery". 3. Under "Write debugging information" section, make sure the "Small memory dump (128KB)" option is selected. 4. Make sure "%SystemRoot%\Minidump" is in the "Small dump directory" open box and click OK. If the Blue Screen appears again, please refer to the following steps to collect memory dump files: 1. Click Start, type %SystemRoot%\Minidump" (without quotation marks) in Search bar and press Enter. 2. Go to your Desktop, right-click on it and create a new folder named "Dump". 3. Copy all the memory dump files (looks like [Mini092008-01.dmp]) in Minidump to this folder. If no clue can be found, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call. To obtain the phone numbers for specific technology request please take a look at the web site listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607 Regards,Arthur Li TechNet Community Support

Hi, You may analyze them with Debugging Tools by yourself. You can install it and its Symbol Packages from the following link: http://www.microsoft.com/whdc/Devtools/Debugging/default.mspx WinDbg will tell you the possible cause. For more information, please read Microsoft KB Article: How to read the small memory dump files that Windows creates for debugging http://support.microsoft.com/kb/315263 Collect Minidump Files ================= 1. Click "Start", input "SYSDM.CPL" (without quotation marks) in the Search bar and press Enter. 2. Switch to the "Advanced" tab and click the "Settings" button under "Startup and Recovery". 3. Under "Write debugging information" section, make sure the "Small memory dump (128KB)" option is selected. 4. Make sure "%SystemRoot%\Minidump" is in the "Small dump directory" open box and click OK. If the Blue Screen appears again, please refer to the following steps to collect memory dump files: 1. Click Start, type %SystemRoot%\Minidump" (without quotation marks) in Search bar and press Enter. 2. Go to your Desktop, right-click on it and create a new folder named "Dump". 3. Copy all the memory dump files (looks like [Mini092008-01.dmp]) in Minidump to this folder. If no clue can be found, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call. To obtain the phone numbers for specific technology request please take a look at the web site listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607 Regards,Arthur Li TechNet Community Support